home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Performance Co-Pilot 1.3
/
SGI Performance Co-Pilot 1.3.iso
/
dist
/
pcp.idb
/
usr
/
share
/
catman
/
u_man
/
cat1
/
pmlogsummary.z
/
pmlogsummary
Wrap
Text File
|
1997-04-03
|
9KB
|
199 lines
PPPPMMMMLLLLOOOOGGGGSSSSUUUUMMMMMMMMAAAARRRRYYYY((((1111)))) PPPPMMMMLLLLOOOOGGGGSSSSUUUUMMMMMMMMAAAARRRRYYYY((((1111))))
NNNNAAAAMMMMEEEE
ppppmmmmllllooooggggssssuuuummmmmmmmaaaarrrryyyy - calculate averages of metrics stored in a PCP archive
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
ppppmmmmllllooooggggssssuuuummmmmmmmaaaarrrryyyy [----aaaabbbbffffllllmmmmMMMMxxxxyyyyzzzz] [----nnnn _n_a_m_e_s_p_a_c_e] [----SSSS _t_i_m_e] [----TTTT _t_i_m_e] [----ZZZZ
_t_i_m_e_z_o_n_e] _a_r_c_h_i_v_e [_m_e_t_r_i_c_n_a_m_e ...]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
ppppmmmmllllooooggggssssuuuummmmmmmmaaaarrrryyyy prints statistical information about metrics of numeric type
contained within the files of a Performance Co-Pilot (PCP) archive log.
The default output prints time averages for both counter and non-counter
metrics. The archive log has the base name _a_r_c_h_i_v_e and must have been
previously created using ppppmmmmllllooooggggggggeeeerrrr(1).
The metrics of interest are named in the _m_e_t_r_i_c_n_a_m_e arguments. If
_m_e_t_r_i_c_n_a_m_e is a non-leaf node in the namespace (see ppppmmmmnnnnssss(4)), then
ppppmmmmllllooooggggssssuuuummmmmmmmaaaarrrryyyy will recursively descend the PMNS and report on all leaf
nodes. If no _m_e_t_r_i_c_n_a_m_e argument is given, the root of the namespace is
used.
Normally ppppmmmmllllooooggggssssuuuummmmmmmmaaaarrrryyyy operates on the default Performance Metrics
Namespace (PMNS), however if the ----nnnn option is specified an alternative
namespace is loaded from the file _n_a_m_e_s_p_a_c_e.
The command line options ----SSSS and ----TTTT can be used to specify a time window
over which metrics should be summarized. These options are common to
most Performance Co-Pilot tools and are fully described in
ppppmmmmPPPPaaaarrrrsssseeeeTTTTiiiimmmmeeeeWWWWiiiinnnnddddoooowwww(3).
The remaining options control the specific information to be reported.
Metrics with counter semantics are converted to rates before being
evaluated.
----aaaa Print all information. This is equivalent to ----bbbbllllmmmmMMMMyyyy ....
----bbbb Print both forms of averaging, that is both stochastic and time
averaging.
----ffff Spreadsheet format - the tab character is used to delimit each field
printed. This option is intended to allow ppppmmmmllllooooggggssssuuuummmmmmmmaaaarrrryyyy output to
import directly into common spreadsheet applications.
----llll Also print the archive label, showing the log format version, the
time and date for the start and (current) end of the archive, and
the host from which the performance metrics values were collected.
----mmmm Also print the minimum logged value for each metric.
----MMMM Also print the maximum logged value for each metric.
PPPPaaaaggggeeee 1111
PPPPMMMMLLLLOOOOGGGGSSSSUUUUMMMMMMMMAAAARRRRYYYY((((1111)))) PPPPMMMMLLLLOOOOGGGGSSSSUUUUMMMMMMMMAAAARRRRYYYY((((1111))))
----xxxx Print stochastic averages instead of the default (time averages).
----yyyy Also print the number of samples encountered in the archive for each
metric.
By default, ppppmmmmllllooooggggssssuuuummmmmmmmaaaarrrryyyy reports the time of day according to the local
timezone on the system where ppppmmmmllllooooggggssssuuuummmmmmmmaaaarrrryyyy is run. The ----ZZZZ option changes
the timezone to _t_i_m_e_z_o_n_e in the format of the environment variable TTTTZZZZ as
described in eeeennnnvvvviiiirrrroooonnnn(5). The ----zzzz option changes the timezone to the local
timezone at the host that is the source of the performance metrics, as
specified in the label record of the archive log.
OOOOUUUUTTTTPPPPUUUUTTTT FFFFOOOORRRRMMMMAAAATTTT
For each metric, ppppmmmmllllooooggggssssuuuummmmmmmmaaaarrrryyyy produces a single output line as follows:
_m_e_t_r_i_c_n_a_m_e _v_a_l_u_e(_s) _u_n_i_t_s
For metrics with possibly multiple instances, ppppmmmmllllooooggggssssuuuummmmmmmmaaaarrrryyyy produces
multiple lines of output as follows:
_m_e_t_r_i_c_n_a_m_e ["_i_n_s_t_a_n_c_e _1"] _v_a_l_u_e(_s) _u_n_i_t_s
_m_e_t_r_i_c_n_a_m_e ["_i_n_s_t_a_n_c_e _2"] _v_a_l_u_e(_s) _u_n_i_t_s
_m_e_t_r_i_c_n_a_m_e ["_i_n_s_t_a_n_c_e _N"] _v_a_l_u_e(_s) _u_n_i_t_s
The printed _v_a_l_u_e(_s) for each metric always follow this order:
stochastic average, time average, minimum, maximum and count. The
individual values for each metric are space-separated (unless the ----ffff
option is used).
All counter metrics which are measured in units of time will be converted
to seconds before being rate converted and used in the ppppmmmmllllooooggggssssuuuummmmmmmmaaaarrrryyyy
calculations. The values calculated for these metrics are also printed
in seconds.
The units will be displayed in the format described by ppppmmmmUUUUnnnniiiittttSSSSttttrrrr((((3333)))).
NNNNOOOOTTTTEEEESSSS
The average for an individual metric is calculated as follows:
Non-counter metrics are averaged using stochastic averaging - each
observation has an equal weighting towards the calculation of the average
(the sum of all values divided by the total number of values, for each
metric).
Counter metrics are averaged using time averaging (by default), but the
----xxxx option can be used to specify that counters be averaged using the
stochastic method instead. When calculating a time average, the sum of
the product of each sample value multiplied by the time difference
between each sample, is divided by the total time over which that metric
was logged.
PPPPaaaaggggeeee 2222
PPPPMMMMLLLLOOOOGGGGSSSSUUUUMMMMMMMMAAAARRRRYYYY((((1111)))) PPPPMMMMLLLLOOOOGGGGSSSSUUUUMMMMMMMMAAAARRRRYYYY((((1111))))
Metrics whose measurements do not span 90% of the archive will be printed
with the metric name prefixed by an asterix (*).
FFFFIIIILLLLEEEESSSS
////vvvvaaaarrrr////ppppccccpppp////ppppmmmmnnnnssss////* default PMNS specification files
////vvvvaaaarrrr////aaaaddddmmmm////ppppccccpppplllloooogggg////_h_o_s_t_n_a_m_e
Default directory for PCP archives containing
performance metric values collected from the host
_h_o_s_t_n_a_m_e.
SSSSEEEEEEEE AAAALLLLSSSSOOOO
ppppmmmmcccchhhhaaaarrrrtttt(1), ppppmmmmdddduuuummmmpppplllloooogggg(1), ppppmmmmllllooooggggggggeeeerrrr(1), ppppmmmmllllooooggggmmmmeeeerrrrggggeeee(1), ppppmmmmvvvvaaaallll(1), PPPPMMMMAAAAPPPPIIII(3),
ppppmmmmUUUUnnnniiiittttSSSSttttrrrr(3), and ppppmmmmnnnnssss(4)....
DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
All are generated on standard error and are intended to be self-
explanatory.
PPPPaaaaggggeeee 3333